home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Tech Arsenal 1
/
Tech Arsenal (Arsenal Computer).ISO
/
tek-06
/
bpt5157.zip
/
BUGS.515
< prev
next >
Wrap
Text File
|
1991-07-29
|
9KB
|
185 lines
1. VAP Btrieve: BSERVER.VAP, version 5.15
When creating a supplemental index, using a null key and an extended
key type, if the null value is an even number, Btrieve will not
recognize the extended key type, but instead use the 3rd bit of the
key flags word to flag the key as either binary or string.
2. NLM Btrieve: BTRIEVE.NLM, version 5.15
After an Update is done on a file with compressed records, positioning
is lost. A Get Position will return a status 8; a Get Next will skip
to the next key value, ignoring the next duplicate, if any. Similarly,
after an Insert is done on a file with compressed record, a
Get Previous will skip to the previous key value, instead of the
previous duplicate, if any.
3. NLM Btrieve: BTRIEVE.NLM, version 5.15
Sometimes a DELETE following a STEP_FIRST, then STEP_PREVIOUS
would return a conflict status 80 because the position was lost on the
failed STEP_PREVIOUS (error #9). This fix restores the position.
4. NLM Btrieve: BTRIEVE.NLM, version 5.15
A system using TTS transactions under heavy load would intermittantly
produce status 14 (Preimage Open Error), with subsequent access
problems until the file is closed and reopened. The problem would
not appear when the BSPXCOM /Workers parameter was set to 1. This fix
implements a semaphore to control TTS task switching and prevent this.
5. NLM Btrieve: BTRIEVE.NLM, version 5.15
VAP Btrieve: BSERVER.VAP, version 5.15
DOS & Windows Btrieve Requesters: BREQUEST.EXE, version 5.16
OS/2 Btrieve Requester: BTRCALLS.DLL, version 5.17
NLM Btrieve Router: BROUTER.NLM, version 5.15
VAP Btrieve Router: BROUTER.VAP, version 5.15
After an Extended Insert, the data buffer should be passed back with
a count of records successfully inserted in the first word of the
buffer. However, this bug prevented the data buffer from being sent
to the application if the Extended Insert returned a non-zero status.
6. NLM Btrieve Router: BROUTER.NLM, version 5.15
When Brouter is used to access a remote server, the application's
data buffer length parameter is always returned unchanged.
7. NLM Btrieve: BTRIEVE.NLM, version 5.15
A Conflict error (status 80) is returned when Updating or Deleting,
even though there is only one workstation accessing the file. This
bug will only appear if the record being updated/deleted contains
a certain pattern of data: all bytes except the first four must be
binary zeroes, and some other, complicated conditions must be met.
8. NLM Bconsole: BCONSOLE.NLM, version 5.15
When number of files opened exceed 400, Resource Usage option
will abend the server.
9. NLM Btrieve: BTRIEVE.NLM, version 5.15
When two clients are pointing at the same record in a file and one of
them does an update which changes its key, the second client will get
an unpredictable, out of sequence record on his next GetNext. This
patch makes his current record invalid but leaves the next and previous
pointers alone to maintain the relative position for that second user.
10. DOS BRequest: BREQUEST.EXE, version 5.16
Due to an incorrect segment usage in the SPXEstablishConnection library
call, 2 bytes of the caller's data area are overwritten whenever a new
connection is made to a Btrieve server. This patch corrects the seg.
11. DOS & Windows Btrieve Requesters: BREQUEST.EXE, version 5.16
NLM Btrieve Router: BROUTER.NLM, version 5.15
This is actually a fix for a bug in patch 5. The symptom is that
garbage is returned in the data buffer after any Get or the Step Next
op returns a status 9.
12. NLM Btrieve: BTRIEVE.NLM, version 5.15
A normally innocuous bug causes protection-check NLMs to break in when
Btrieve NLM is UNLOADING due to writes to a byte of memory just FREE'd.
This patch uses other memory to avoid this annoyance.
13. VAP Btrieve: BSERVER.VAP, version 5.15
When all workstations are shut down on an ArcNet network, the VAP
operating system returns an error to all VAPs using the Service
Advertising Protocol. This causes Bserver to issue an Error-Log message
of "Send Failure in Advertiser". This patch is normally commented-out,
but may be enabled by users who find their error logs clogged up.
14. VAP Btrieve: BSERVER.VAP, version 5.15
With multiple workstations involved in transactions, a client could
receive erratic and non-repeatable status 2s on operations ranging from
OPENs to GETs on a file already opened. The root cause is that one
client has opened the file to his TTS task and the file has subsequently
been closed for rotation due to limited handles. The problem is that
the file must be re-opened on the next access, but only the owner task
can do so. All others get errors that translate to 2. The problem
disappears as soon as the first client accesses or ends his transaction.
This bug is therefore timing-related and very hard to pin down. This
fix allows other clients to temporarily assume the right task #.
16. Btrieve (DOS, Windows, OS/2, VAP)
The STAT command would return 0 for unused pages whenever the number was
greater than 32K (32768). This forces a non-zero return.
17. BTRIEVE (NLM)
Fixes a problem in patch 9 which causes the following problem: after
an Update which changes a record's key value, a subsequent
Get Previous skips any records whose key value is a duplicate of
the (new) key value of the record which was just changed.
19. VAP Btrieve: BSERVER.VAP, version 5.15
Fixes the problem described in Patch 9 for bserver.vap.
20. VAP Btrieve: BSERVER.VAP, version 5.15
When building a supplemental index (Op 31) on a file opened in
accelerated mode, if a duplicate key value is found and duplicates are
not allowed for the index being built, btrieve enters an infinite loop.
23. VAP Btrieve: BSERVER.VAP, version 5.15
If you don't establish position and execute Btrieve Get Position op.
it will return status 0 instead of 8. This op. also returns a status
of 0 when it has been done on an empty file.
This patch corrects position information set by open operation.
24. NLM Btrieve: BTRIEVE.NLM, version 5.15
GET NEXT/PREVIOUS KEY operation should be faster than GET NEXT/PREVIOUS
operation, because it only retrieves the key value from the file.
The fact is that it is slowlier. This patch makes the tuched KEY_BIAS
operations are not converted to GET_GT/GET_LT operations, that's why the
performance has been improved. (BTRIEVE DOS v5.10a patch #102)
25. NLM Btrieve: BTRIEVE.NLM, version 5.15
This fixes a bug in an undocumented Btrieve function call which is
used by NetWare SQL in its "alter table" function. The bug may abend
the server.
26. NLM Btrieve: BTRIEVE.NLM, version 5.15
This fixes a bug which allowed a Drop_Supplemental_Index call to procede
on a file which was locked in a transaction by another user, disrupting
that user's transaction. Like DOS, it now returns FileInUse, error# 85.
27. NLM Btrieve: BTRIEVE.NLM, version 5.15
After opening a file and starting a transaction for insert records and
during the transaction making a reboot, the transaction and the file
have been left open. This was caused by a failure of the BSPXCOM
watchdog-reset mechanism to reset the user.
This patch fixes the bug by setting and checking the NOT_IN_TABLE value
of Client at several places.
28. NLM Btrieve: BTRIEVE.NLM, version 5.15
When the 'create supplemental index' operation returned a non-zero
status the server hung up. This was caused by a failure of the
'drop supplemental index' algorithm.
29. NLM Btrieve: BTRIEVE.NLM, version 5.15
'Create supplemental index' doesn't skip records with null-value keys
though the manual key flag has been set in the key-description file.
The condition to determine if checking_for_null-key_values is necessary
or not was faulty.
***** Last Update - 07/10/91 - KR *****